Skip to content

[BUG] Invalid packageManager is added to package.json #1274

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
2 of 3 tasks
cheesestringer opened this issue Apr 27, 2025 · 0 comments
Open
2 of 3 tasks

[BUG] Invalid packageManager is added to package.json #1274

cheesestringer opened this issue Apr 27, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@cheesestringer
Copy link
Contributor

cheesestringer commented Apr 27, 2025

What happened?

I'm using npm as my package manager of choice.
When I run commands like npm run dev or npm run build a new packageManager field with value pnpm is added to the package.json.

The packageManager shouldn't be guessed and it should be up to the user to add it to their package.json. Setting the value to npm@version will stop Plasmo interfering but this isn't something I'd want to include in my project until the field supports version ranges nodejs/corepack#95.

Version

Latest

What OS are you seeing the problem on?

Windows

(OPTIONAL) Contribution

  • I would like to fix this BUG via a PR

Code of Conduct

  • I agree to follow this project's Code of Conduct
  • I checked the current issues for duplicate problems.
@cheesestringer cheesestringer added the bug Something isn't working label Apr 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant